Fragment Servitor
A fragment servitor is only capable of one highly specific function. It generally has no nuance to it whatsoever but is instead used to provide nuance/support to simple and complex servitors.
What would be an example of a fragment servitor? I'm assuming you have created a fragment servitor or at least thought of creating one, if you did what was it designed for and what did it do? (edited)a fragment would be
input>turn crimson
and the simple servitor would be
{[detect stimulus>send output]>[detect input>turn crimson]>[detect colour change>send output]>[(detect input>send output)>(detect input>send output outside of program)]>[detect input>self stimulate]>[detect self stimulation>turn grey]}
and that's the entire simple servitor for the pain response
All of this is a good example of what a fragment is vs a simple servitor. While you can make up a hypothetical servitor if you wanted too, this alone is the right idea for an example.
Since it seems like there's a hierarchy of complexity, it may be easier to think of one complex servitor example and break the servitor down into its simple and fragment parts. (I don't think I'm doing this right) if I had a GUI servitor (complex), the simple parts would be the layout settings, the button to show the body scan, etc. The body scan servitor we have is made up of fragments [input>anxiety]>[return image]. In this case, I would start with the simple fragment for the body scanner, then explain the body scanner, and then explain the GUI where the body scanner is accessible via a command.
I hope I didn't make that too confusing, I'm not an expert in this approach to servitor creation (edited)